Issue & Reproduction Steps

The BPMN files generated by the modeler used by the client cannot be imported into PM. However, it works perfectly with other BPMN files from different modelers.

Solution

The XSD definition used by ProcessMaker restricts some definitions found in the client’s BPMN files. A couple of these restrictions have been modified to allow the client’s files to be imported.

How to Test

Create a new process and use one of the BPMN files provided in the ticket.

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-25187

Important Note

With this change, the BPMN files provided by the client can be imported. However, our modeler does not automatically fix the visual layout of certain elements in their designs (likely due to differences in scaling and icon sizes between the two modelers).

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.